Next generation mobility core network controller for service delivery

ABSTRACT

Network and/or application resources can be dynamically instantiated based on service attributes and/or network capabilities. In one aspect, a customized and/or localized core slice can be selected that can deliver the requested service with target performance parameters. According to an aspect, dynamic selection, control, and/or management reporting can be provided for core network slices. Moreover, optimal core network slice selection can be performed to reduce network transport costs and efficiently deliver various services using an optimal core slice that matches a service profile being requested by an end user and/or device.

TECHNICAL FIELD

The subject disclosure relates to wireless communications, e.g., nextgeneration mobility core network controller for service delivery.

BACKGROUND

Communication networks are built with access network and core networkcontrol functions. The access network control function provides edgecomputing control for a multitude of devices, that have been grantedaccess to the core network, to perform a target service. Further, thecore network control function performs control functions associated withappropriate destinations according to defined criteria to deliver therequested services. A mobility access network function comprises edgecontrol functions and radio/access components that can support differentaccess technologies, for example, cellular, WiFi, Bluetooth™, and/orother low power radio networking technologies, etc. A mobility corenetwork function comprises control plane (CP) and user plane (UP) datahandling mechanisms. Typically, the control functions utilizeinformation from network databases (e.g., home subscriber database(HSS)) to determine a policy(ies) for each service request associatedwith the devices. The UP anchors and executes the commands from the CPand routes the user data traffic pertaining to a given end userrequested service. In order to improve efficiency for service delivery,multiple slices of the core network are built for different services,wherein each core network slice can be equipped with different CP and UPdata transfer functions and/or policies. Conventional networks utilizenetwork selection mechanisms that are radio access network (RAN)directed, with limited information, and wherein cross-nodal redirectionsare often performed. This significantly increases network signalingand/or processing times and reduces overall network efficiency,resulting in higher capital and operating costs. Typically, the RAN ispre-configured to direct a service request to a specific core networknode to complete a connection/session setup prior to receiving itsservices. In particular, conventional networking design is static withpre-configured mappings defined per given RAN. This results in aninefficient allocation and utilization of several core network functionsand their associated resources serving the RAN technology deployed forservice delivery.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system that facilitates dynamic allocationof core network slices of a communication network.

FIG. 2 illustrates an example system for managing core network slicesbased on dynamically determined triggers.

FIG. 3 illustrates an example system that determines triggers tofacilitate optimal core network slice selection.

FIG. 4 illustrates an example system that provides dynamic core networkslice allocation.

FIG. 5 illustrates an example system that facilitates monitoring of corenetwork slices.

FIGS. 6A-6B illustrates example systems that facilitate automating oneor more features in accordance with the subject embodiments.

FIG. 7 illustrates an example method that facilitates allocation of corenetwork resources.

FIG. 8 illustrates an example method that facilitated selection of anoptimal core network slice for handling a service request.

FIG. 9 illustrates a block diagram of a computer operable to execute thedisclosed communication architecture.

FIG. 10 illustrates a schematic block diagram of a computing environmentin accordance with the subject specification

DETAILED DESCRIPTION

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It may be evident,however, that the various embodiments can be practiced without thesespecific details, e.g., without applying to any particular networkedenvironment or standard. In other instances, well-known structures anddevices are shown in block diagram form in order to facilitatedescribing the embodiments in additional detail.

As used in this application, the terms “component,” “module,” “system,”“interface,” “node,” “platform,” “server,” “controller,” “entity,”“element,” “gateway,” or the like are generally intended to refer to acomputer-related entity, either hardware, a combination of hardware andsoftware, software, or software in execution or an entity related to anoperational machine with one or more specific functionalities. Forexample, a component may be, but is not limited to being, a processrunning on a processor, a processor, an object, an executable, a threadof execution, computer-executable instruction(s), a program, and/or acomputer. By way of illustration, both an application running on acontroller and the controller can be a component. One or more componentsmay reside within a process and/or thread of execution and a componentmay be localized on one computer and/or distributed between two or morecomputers. As another example, an interface can comprise input/output(I/O) components as well as associated processor, application, and/orAPI components.

Further, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement one or moreaspects of the disclosed subject matter. An article of manufacture canencompass a computer program accessible from any computer-readabledevice or computer-readable storage/communications media. For example,computer readable storage media can comprise but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips. . . ), optical disks (e.g., compact disk (CD), digital versatile disk(DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick,key drive . . . ). Of course, those skilled in the art will recognizemany modifications can be made to this configuration without departingfrom the scope or spirit of the various embodiments.

In addition, the word “example” or “exemplary” is used herein to meanserving as an example, instance, or illustration. Any aspect or designdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or.” That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform.

Moreover, terms like “user equipment,” “communication device,” “mobiledevice,” “mobile station,” and similar terminology, refer to a wired orwireless communication-capable device utilized by a subscriber or userof a wired or wireless communication service to receive or convey data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream. The foregoing terms are utilized interchangeably inthe subject specification and related drawings. Data and signalingstreams can be packetized or frame-based flows. Further, the terms“user,” “subscriber,” “consumer,” “customer,” and the like are employedinterchangeably throughout the subject specification, unless contextwarrants particular distinction(s) among the terms. It should be notedthat such terms can refer to human entities or automated componentssupported through artificial intelligence (e.g., a capacity to makeinference based on complex mathematical formalisms), which can providesimulated vision, sound recognition and so forth.

Aspects or features of the disclosed subject matter can be exploited insubstantially any wired or wireless communication technology; e.g.,Universal Mobile Telecommunications System (UMTS), WiFi, WorldwideInteroperability for Microwave Access (WiMAX), General Packet RadioService (GPRS), Enhanced GPRS, Third Generation Partnership Project(3GPP) Long Term Evolution (LTE), Third Generation Partnership Project 2(3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA),Zigbee, or another IEEE 802.XX technology, Fifth generation (5G), etc.Additionally, substantially all aspects of the disclosed subject mattercan be exploited in legacy (e.g., wireline) telecommunicationtechnologies.

Dedicated core networks (DCN) is an optional 3GPP standards-definednetwork feature capability that enables an operator to deploy multipleinstances of core networks (e.g., core network slices) within a servinghome public land mobile network (HPLMN). A dedicated core network slicecan comprise selected control and/or traffic forwarding functions, whichdetermine a subscriber's eligibility for the network service, theservices the subscriber has requested, and/or a path to route thetraffic associated with the service to appropriate destinations. In oneor more traditional core network deployments, a radio access network(RAN) is pre-configured to direct traffic, from a user equipment to agiven core network node, to complete a connection/session setup prior toreceiving its services. The traditional mechanisms of mobility corenetworking design are static with pre-configured mappings defined pergiven RAN. This results in an inefficient allocation and utilization ofcore network functions and their associated resources serving the RANtechnology deployed for services delivery.

One or more embodiments of the subject disclosure provide a core networkcontrol selection mechanism that allocates an end user/machine devicebased on its service requests and radio capabilities to a suitable(e.g., customized and/or localized) core network slice that can deliverthe requested service with target performance attributes. Typically,next generation global communication and connectivity networks (e.g.,fifth generation (5G) networks) are characterized by software definednetworking (SDN) principles, heavy cloud computing, control plane (CP)and user plane (UP) data separation, radio access agnostic core networkcontrol, etc. The systems and methods disclosed herein, in one or morenon-limiting embodiments, provide dynamic and intelligent selection,flexible reconfiguration, control, reconfigurations, and/or managementreporting for core network slices of the core communication network.According to an aspect, the systems and/or methods enable optimalnetwork selection and/or reconfiguration in order to reduce the networktransport cost and efficiently deliver various services using an optimalcore network slice that best fits the service profile (and/or multiplesimilar service profiles) being requested by the end user and/or device.

Referring initially to FIG. 1, there illustrated is an example system100 that facilitates dynamic allocation of core network slices of acommunication network, according to one or more aspects of the disclosedsubject matter. As an example, a core network of a communication networkcan comprise devices (e.g., gateways, servers, data stores, etc.) thatprovide communication services to user equipment (UE), which areconnected to the communication network via a wired and/or wirelessaccess network (e.g., radio access network (RAN)). Future communicationservices demand a flexible and software programmable network that cansupport a broad range of applications that have different servicerequirements/attributes. System 100 provides an efficient core networkcontrol selection mechanism that allocates the UE based on its servicerequests and radio capabilities to a suitable core slice that candeliver the requested service with target performancerequirements/attributes.

The DCN feature capability utilized in conventional systems has severallimitations in the way redirections are performed between the access andcore network elements and lacks dynamic function reconfiguration andinsertion within a service chain. Further, the principles employed bythe conventional systems cannot be generically applied between multipleradio access technologies and core networks. At a high level, DCN isnetwork based solution, wherein depending on subscriber profile storedin a network database (e.g., HSS), LTE evolved packet core (EPC) corenetwork control nodes, like mobility management entity (MME), indicateto the RAN control node, when a UE attaches to the network, a specificDCN control node to which traffic is to be steered. Moreover, during aUE's initial network attach/tracking area update procedure, aconventional radio network control node does not have detailedinformation about the device type and/or its supported services, andmerely selects a control node (e.g., MME) in a DCN via pre-configuredand/or static logic in the access and core network. When the UE isconnected to the MME (e.g., via a non-access stratum (NAS) layer), theMME can retrieve a subscriber profile associated with the UE from theHSS, and send, to the RAN control node, correct DCN information, in casethe UE is not connected to the correct MME. This results in aredirection, wherein the radio network control node will reconnect theUE to the correct DCN per first control node's direction. Further, sincethere is limited information provided by the UE during initialcorrespondence with the eNodeB (eNB) and lack of device specificintelligence extracted in the eNB, oftentimes the eNB does not send theUE attach request to the correct control node (MME) for the first time,and thus the number of DCN redirections performed is significant.Furthermore, the DCN redirections can be performed during a UE handoverand/or when a subscriber profile (associated with the UE) is updated.These conventional redirection procedures during device initial networkattach and/or hand-over result in unnecessary CP signaling between theaccess and core network functions and increased message processingtimes, eventually causing incremental and/or unwanted network costs.This can negatively affect network performance and services delivery.Some conventional systems provide enhancements to improve the usernetwork selection logic, wherein current subscriber profile parametersare retrieved from HSS by an MME and utilized to facilitate networkselection. However, these systems have limited efficiency incoordinating the core network selection since device services and/ornetwork performance optimization is not considered.

Steering a UE to the correct control node during an initial signalingphase is critical to speed up the connection establishment processen-route to rapid service instantiation. Independent of the nature ofthe network function evolution coupled with their operations supportsystems (OSS) design (e.g., physical and/or virtualized platforms),efficient utilization of overall network resources is key to maintaininglow capital and/or operating costs while delivering enhanced valueand/or effortless service experience to end users/machines. According toan aspect, system 100 provides a service abstraction component 102 thathas a full insight into all the network layers (e.g., RAN, core network,and/or transport network layers). In one example, the serviceabstraction component 102 facilitates directing a UE to a correctcontrol node (of a selected and/or a reconfigured network slice which isoptimal for one more services) during the initial signaling phase basedon facilitating interoperability between a radio network controlcomponent 104, a transport network control component 106, and a corenetwork control component 108. As the technology evolves to aggregatemultiple radio access edge networks with an open standards basedinterface to a common core transport, the service abstraction component102 can provide a dynamic, intelligent, and/or controlled means ofdirecting the UE to a targeted core network slice that can deliverend-to-end service values by respecting network design and deploymentprinciples.

In one aspect, the service abstraction component 102 can reduce thenetwork capital costs in design and/or building of the core network andcan improve the overall efficiency in operating and/or monitoring ofvarious network functions involved in a delivery of mobility servicesfor consumers, enterprises, and/or government solutions etc. Further,the service abstraction component 102 can provide efficient connectivityof UEs in the network across several industry verticals leading to newbusiness models, which can result in driving high-speed mobile socialnetworking changes that were not possible with conventional systems.

According to an embodiment, the radio network control component 104 canaggregate information associated with different access points deployedwithin a region and provide the information to the service abstractioncomponent 102. In one example, the access points can operate usingdifferent radio access technologies, such as, but not limited to, 4G,5G, 3G, WiFi, low power wide area networks, and/or other non 3GPPtechnologies. Similarly, the transport network control component 106 canaggregate information associated with different devices (e.g., routersand/or switches hosted on central office and/or switching officeenvironments) of backhaul networks that are on the egress and/or ingressof the infrastructure between the RAN and core network, and provide theinformation to the service abstraction component 102. For example, thebackhaul networks can comprise, but are not limited to, wired networks,wireless networks, satellite networks, microwave networks, meshnetworks, optical infrastructure, etc. In one aspect, the serviceabstraction component 102 can analyze the information to provideappropriate triggers to the core network control component 108 that canbe utilized to manage existing and/or create new core network slices forserving UEs or a specific class, requesting a specific service, and/orare located within a specific area.

The core network control component 108 can be utilized to manage (e.g.,instantiate, update, delete, etc.) one or more network slices of corenetwork. In one example, a network slice can comprise a logical/virtualreplication of core network elements employed to enable a specifiedservice. Moreover, the network slices can comprise virtual networksbuilt on top of a common/shared physical infrastructure. As an example,the virtual networks refer to implementing the functions ofinfrastructure nodes in software on commercial “off-the-shelf” computingequipment. Virtualization can decrease capital and/or operating costs,reduce time for deployment of new services, improve energy savings,and/or enhance network efficiency. In one aspect, the network slices canbe customized (e.g., in terms of resources allocated, latency,bandwidth, etc.) for respective services handled by the network slices.This enables operators to provide software programmable networks andfunctions on an as-a-service basis and/or functions/components on anas-a-service basis, which can significantly improve operationalefficiency and/or reduce time-to-market for new services. In oneexample, the network slices can be implemented via one or more gatewaydevices (e.g., legacy gateways, control plane gateways and/or user planegateways) that perform functions of, but not limited to, switches,routers, repositories, policies, home location register (HLR), servingGPRS support node (SGSN), gateway GPRS support node (GGSN), combinedGPRS support node (CGSN), radio network controller (RNC), servinggateway (SGW), packet data network gateway (PGW), residential gateway(RGW), broadband remote access server (BRAS), carrier grade networkaddress translator (CGNAT), deep packet inspection (DPI), provider edge(PE) router, mobility management entity (MME), element management system(EMS), etc.

The architecture disclosed in system 100 facilitates application ofnetwork functions virtualization (NFV) and/or software-definednetworking (SDN) technologies. NFV can virtualize network services thathave been conventionally carried out by proprietary, dedicatedhardware/software and instead host the network services on one or morevirtual machines (VMs). Using NFV, network service providers do not needto purchase proprietary/dedicated hardware devices to enable a service.NFV can improve scalability and flexibility and network capacity caneasily be adjusted through software, resulting in reduced capitalexpenses and/or operating expenses. NFV and SDN are differenttechnologies but complementary. SDN architectures decouple ordisassociate network control (e.g., control plane) and forwarding (e.g.,data plane) functions. This allows for dynamic, programmable, and/orscalable computing and storage. The SDN architecture can be at least (i)directly programmable; (ii) agile; (iii) centrally managed; (iv)programmatically configured; and/or (v) open standards-based andvendor-neutral.

In one example, system 100 can be deployed in 5G networks that provideenhanced mobile broadband, for example, ultra high bandwidth (e.g., 20Gbps), high spectral efficiency (e.g., 3.5× of LTE), ultra densenetworks, and/or energy efficiency. Further, the 5G networks can provideultra-reliable (e.g., high reliability greater than 99.999%) and lowlatency communications (e.g., ultra low latency of ˜1 msec and/or lownetwork access and synchronization time). Furthermore, the 5G networkscan facilitate massive machine type communication (e.g., ultra highdensity (10⁶/sq km), long battery life (10 years+), high system gain(better than narrow band-IoT and/or more efficient than narrowband-IoT).

Referring now to FIG. 2, there illustrated is an example system 200 formanaging core network slices based on dynamically determined triggers,in accordance with an aspect of the subject disclosure. It is noted thatthe service abstraction component 102, the radio network controlcomponent 104, the transport network control component 106, and the corenetwork control component 108 can comprise functionality as more fullydescribed herein, for example, as described above with regard to system100. Although system 200 has been described with respect to a 5Gnetwork, it is noted that the subject disclosure is not limited to 5Gnetworks and can be utilized in most any communication network.Moreover, system 200 can be utilized to provide an intelligent,flexible, and dynamic network architecture that can enable both networkoperators and service/application providers in delivering a customizedservice.

According to an embodiment, UEs 1-N (202 ₁-202 _(N); wherein N is mostany natural number) can connect to the communication network via one ormore radio networks 204. As an example, the UEs 1-N (202 ₁-202 _(N)) cancomprise, but are not limited to most any industrial automation deviceand/or consumer electronic device, for example, a tablet computer, adigital media player, a wearable device, a digital camera, a mediaplayer, a cellular phone, a personal computer, a personal digitalassistant (PDA), a smart phone, a laptop, a gaming system, set topboxes, home security systems, an Internet of things (IoT) device, aconnected vehicle, at least partially automated vehicle (e.g., drones),etc. In one aspect, the radio networks 204 can comprise most any accessnetwork such as, but not limited to, 3G, 4G, 5G, WiFi, low power widearea, and/or other non 3GPP networks. In one aspect, RAN data store 206can store information related to the radio networks 204, such as but notlimited to, spectrum data, access point information, cell siteinformation, geographical location data, load, cell identifier, type ofaccess point (e.g., macro, femto, pico, etc.), the access networkservice chains, functional blocks and/or mode of operations of theaccess network service chains, etc. As an example, when an access pointof radio networks 204 is installed and/or activated, the access pointcan provide its information to the RAN data store 206 (and/or can updatethe information periodically and/or in response to an event). In anaspect, the service abstraction component 102 can utilize theinformation stored within the RAN data store 206 to facilitateselection, reconfiguration, and/or instantiation of a customized corenetwork slice for a service.

According to an embodiment, UEs 1-N (202 ₁-202 _(N)) can transmit arequest for a service (e.g., streaming video, navigation service,content delivery service, emergency service, etc.) via an access pointof the radio networks 204. On receiving the request, the radio networkcontrol component 104 can provide a trigger to the service abstractioncomponent 102, which can then determine a type of the service, thequality of experience (QoE) expected for the service, informationrelated to the access network (e.g., from RAN data store 206),information related to the transport routers 208 (e.g., from thetransport network control component 106), etc., to provide a trigger(e.g., with information regarding service requirements/attributes for aparticular class of devices, latency, network conditions, location ofaccess point, etc.) to the core network control component 108. Based onthe trigger, the core network control component 108 can determinewhether to utilize a pre-dedicated core network slice, update thepre-dedicated core network slice, or instantiate a new core networkslice of the core network slices 1-M (210 ₁-210 _(M); wherein M is mostany natural number) to handle the requested service. For example, thecore network control component 108 can allocate a pre-dedicated (e.g.,already instantiated) core network slice that comprises a defined set offunctions that satisfy the service request or can instantiate on-demandand allocate, a new core network slice that is an optimal slicecomprising only the essential functions required to handle the servicerequest. In one aspect, for a more delay tolerant service, the corenetwork control component 108 can instantiate the pre-dedicated corenetwork slice, while for less delay tolerant service, the core networkcontrol component 108 can create a new logic service function chain inthe pre-dedicated core network slice (e.g., reconfigure thepre-dedicated core network slice) or spin the new core network slicethat comprises devices that located geographically closer to (e.g.,within a defined distance from) the RAN to which the UE has connected.As an example, the core network slices 210 ₁-210 _(M) can communicate,via an IP network 212, with one or more application servers (AS) 1-K(214 ₁-214 _(K); wherein K is most any natural number) associated withthe service.

In an aspect, the service function chain in a network slice can comprisea group of functional blocks and/or components that are “chainedtogether” (e.g., coupled together) to fulfill attributes, such as butnot limited to, service requirements and/or an expected QoE of arequested service in the respective network type (e.g., RAN, wirelesscore network, WiFi access network, etc.). Each functional block and/orcomponent can be instantiated in a full-support mode, a semi-transparentmode, or a full-transparent mode for different service data flowsutilizing the same network slice. This particular concept of servicefunction and/or service component configuration/reconfiguration in anetwork slice provides even more flexibility and efficiency in thenetwork slicing architecture.

According to an embodiment, subsequent to the core network sliceallocation, the service abstraction component 102 can facilitatesynchronization of the radio network control component 104 and corenetwork control component 108 to exchange network address data thatprovides the access point serving the UE with the network address of thecore network element (e.g., MME), to which traffic for the service isfor be steered. It is noted that the RAN data store 206 can includevolatile memory(s) or nonvolatile memory(s), or can include bothvolatile and nonvolatile memory(s). Examples of suitable types ofvolatile and non-volatile memory are described below with reference toFIG. 9. The memory (e.g., data stores, databases) of the subject systemsand methods is intended to include, without being limited to, these andany other suitable types of memory.

Referring now to FIG. 3, there illustrated is an example system 300 thatdetermines one or more triggers to facilitate optimal core network sliceselection, in accordance with an aspect of the subject disclosure. It isnoted that the service abstraction component 102 can comprisefunctionality as more fully described herein, for example, as describedabove with regard to systems 100 and 200. In one example, the serviceabstraction component 102 can comprise a data reception component 302that can receive request-related information from various networkdevices. In one aspect, the data reception component 302 can receive atrigger from the radio network control component 104 when a servicerequest is received from a UE by an access point coupled to the radionetwork control component 104. The data reception component 302 can thendetermine information related to the access point (e.g., from the RANdata store), information related to the UE (e.g., devicecharacteristics, subscriber profile data, etc.), and/or informationrelated to the service (e.g., type of service, latency requirements,quality of service, etc.). Further, the data reception component 302 cancollect status information (e.g., load, performance, etc.) related tothe transport layer from the transport network control component 106.Additionally or optionally, the data reception component 302 can collectdata from one or more network and/or third party servers, for example,but not limited to event data (e.g., time/location details regarding anevent), weather data, traffic data, etc.

According to an aspect, an analysis component 304 can evaluate theinformation collected by the data reception component 302 to determineone or more triggers that are provided to the core network controlcomponent 108. For example, the triggers can include, but are notlimited to, information indicative of a radio access type supported bythe UE, whether the UE has attached to the network using a preferredradio access technology, a change in a location of the UE due tomobility events, speed of the UE, other services requested by the UE,home network re-classification for the UE, network initiated homenetwork resources dynamic modification and/or re-allocation forperformance optimization, and/or network initiated UE rehoming (e.g.,due to service priority and/or performance needs), etc.

Referring now to FIG. 4, there illustrated is an example system 400 thatprovides dynamic core network slice allocation, according to an aspectof the subject disclosure. It is noted that the core network controlcomponent 108 can comprise functionality as more fully described herein,for example, as described above with regard to systems 100-200. Althoughsystem 400 has been described with respect to a 5G network, it is notedthat the subject disclosure is not limited to 5G networks and can beutilized in most any communication network.

According to an aspect, a slice management component 402 can be utilizedto allocate service requests to different core network slices. In oneaspect, the slice management component 402 can determine whether apre-dedicated core network slice (e.g., that has already beeninstantiated) is to be allocated for a particular service request orwhether a new core network slice is to instantiated to handle theparticular service request. In one aspect, the determination can bebased on triggers received from the service abstraction component 102,historical data, slice loads and/or performance, service function chainre-configurability in a pre-dedicated core network slice, operatorand/or service provider defined policies/preferences, etc. As anexample, the slice management component 402 can select an optimal corenetwork slice (existing or new) that is customized for a servicerequested by a UE based on information (e.g., received from the serviceabstraction component 102 and/or radio network control component 104),such as, but not limited to, a UE profile (e.g., comprising UE type data(e.g., IoT, smartphone, tablet, etc.) UE category (CAT-0, CAT-1,CAT-3/4, CAT-M, and the like), usage types, access priority,communication and mobility characteristics, access technology supportedby the UE, billing characteristics, etc.), UE location (e.g.,geographical location, home or roaming/visiting, etc.), service(s)requested (e.g., type of service), UE and/or network/business basedpolicies, local and/or global network load and/or performance conditions(e.g., real-time and/or current network load and/or performance), etc.

In one aspect, the slice management component 402 can exchange accesstype data with the radio network control component 104 prior to corenetwork resource slice allocation. Moreover, the slice managementcomponent 402 can handle (e.g., allocate resources for) service requestsfrom UEs across different access technologies and facilitate servicedelivery via an optimal transport routing path. In one example, theslice management component 402 can allocate control plane and/or userplane supporting functions within a core network slice based on the typeof service requested by the UE and/or the device class/category of theUE. Further, the slice management component 402 can dynamically reroutetraffic in-service associated with a given UE and/or service based onits priority. As an example, the slice management component 402 canmaintain UE context synchronization with the radio network controlcomponent 104 for the service duration.

The services requested by the UE can be associated with a wide range ofapplications that can be performed by utilizing different networkfunctions. Based on an analysis of information, such as but not limitedto, service requirements/attributes for a particular class of devices,latency, network conditions, etc., the slice management component 402can allocate resources for a particular service. In one example, theslice management component 402 can instantiate a pre-dedicated (e.g.,already instantiated) core network slice comprising a defined set offunctions that satisfy the service request or can instantiate,on-demand, a new core network slice customized for the service request(e.g., that comprises only the essential functions required to handlethe service request).

As an example, core network slice 210 ₁ (e.g., comprising MME, HSS,serving/PDN gateway (S/P-GW), policy and charging rules function (PCRF),session border controller (SBC), call session control function (CSCF),and service centralization and continuity application server (SCC-AS)functions) can be allocated for traffic associated with a voice over LTE(VoLTE) service 404 ₁; core network slice 210 ₂ (e.g., comprising MME,HSS, S/P-GW, policy and charging rules function (PCRF), servicecapability or network exposure function (SCEF/NEF), automotiveapplication server (AS) functions) can be allocated for trafficassociated with automotive Internet of things (IoT) services thatutilize high network bandwidth 404 ₂; core network slice 210 ₃ (e.g.,comprising MME, HSS, SCEF/NEF, AS functions) can be allocated fortraffic associated with smart city UEs 404 ₃ (e.g., IoT utility metersthat utilize low network bandwidth); core network slice 210 ₄ (e.g.,comprising MME, mobile switching center (MSC), HSS, short messageservice center (SMSC)/converged IP messaging (CPM), machine typecommunication interworking function (MTC-IWF), SCEF/NEF, AS functions)can be allocated for traffic associated with short messaging services404 ₄ for IoT devices; core network slice 210 _(M) (e.g., comprisingMME, HSS, evolved serving mobile location center (ESMLC), gateway mobilelocation center (GMLC) functions) can be allocated for trafficassociated with location based services 404 _(M), and the like.

As another example, core network slices 210 ₂, 210 ₃, and/or 210 ₄ canbe a single network slice dedicated for IoT Services. Depending onservice requirements, a logic service function chain can be created forthe service data flow. Certain functional blocks and/or components arefully functional in the chain while others may operator in thetransparent mode, e.g., in slice 210 ₃, the S/PGW and the PCRF can be inthe transparent mode.

As noted above, the slice management component 402 can determine whethera pre-existing core network slice is to be utilized for a servicerequest or a new (customized and/or localized) core network slice is tobe instantiated and utilized for the service request. For example, ifdetermined that the service satisfies a defined latency criteria (e.g.,is delay tolerant) and/or does not have (or has minimal) functionalblocks reconfigurations, the pre-existing core network slice can beutilized, whereas if determined that the service fails to satisfy thedefined latency criteria (e.g., is not delay tolerant) and/or potentialreconfiguration of the functional blocks is too costly for the requestednew data service flow, the new core network slice can be instantiatedand utilized for the new data service flow. In one aspect, the new corenetwork slice can be geographically closer to the RAN (serving the UEthat requested the service). As an example, during an event, such as aconcert, game, rally, parade, etc., the service abstraction component102 can determine an increase in UE density in a given area (e.g., basedon UE density information stored within the RAN data store 206 and/orevent data received from one or more servers) and provide an appropriatetrigger to the core network control component 108, which can then (e.g.,via the slice management component 402), spin an instance of a corenetwork slice that is geographically closer to the event location (e.g.,as compared to the existing core network slices) to efficiently andquickly address the spike in traffic demand and/or guarantee improvedservice performance. Once the event is over (e.g., as determined by theservice abstraction component 102), the slice management component 402can deinstantiate the resources and use the predefined slices to handlesubsequent traffic having lower/normal demand (e.g., more delay toleranttraffic) from UEs within the event location.

In another example, for requests received from a particular type of UE(e.g., CAT-1, CAT-M, etc.) within a specified location, the serviceabstraction component 102 can send, to the core network controlcomponent 108, a trigger that indicates a group type event. In responseto receiving this trigger, the slice management component 402 can createa new localized slice that is close to (e.g., within a defined distancefrom and/or closer than the other core network sliced to) the specifiedlocation to handle traffic from UE's that belong to the particular typeand that are located within the specified location. Additionally oralternatively, the slice management component 402 can determine whethera new localized slice is to be created based on loading statistics ofthe existing core network slices. For example, if the load associatedwith the existing core network slice 201 ₁ is greater than a definedthreshold and/or the temporary traffic peak is localized, the slicemanagement component 402 can instantiate a new localized slice to handlea subsequent VoLTE service request for the location. Further, in anotherexample, the slice management component 402 can determine whether a newlocalized slice is to be created based on determining that a customizedset of functions (and/or location of the functions) can provide asuperior performance than the performance that would be provided byexisting core network slices. For example, on receiving a request for aIoT SMS service that utilizes a direct interface (e.g., SGd interface)between the MME and the SMSC, the slice management component 402 candetermine that utilizing a new (and optionally localized) core networkslice comprising customized functions (e.g., MME, HSS, SMSC/CPM,MTC-IWF, SCEF/NEF, and AS) can provide a better performance than corenetwork slice 210 ₄, and accordingly, instantiate the new core networkslice to handle traffic associated with the IoT SMS service request.Furthermore, in yet another example, the slice management component 402can determine whether a new localized slice is to be created based onrevenue generation and/or priority policies. For example, for highpriority services (e.g., emergency services) and/or services that areassociated with high (e.g., greater than a defined threshold) revenuegeneration, the slice management component 402 can instantiate a newcustomized and/or localized core network slice.

It is noted that the slice management component 402 is not limited tovertical network slicing (e.g., one RAN slice, one wireless core sliceand one service core slice for an end-to-end network slice), but canalso facilitate horizontal slice management for the end-to-end networkarchitecture. In one aspect, one core network slice can support multipleRAN slices with a single core network slice with different servicefunction chains in order to achieving efficiency and reduce the networkmanagement overhead. Moreover, a network slice is not monolithic andcomprises a set of network functions/components that can form a servicefunction chain in multiple ways, wherein each function/component can beoperated in multiple modes. For a example, the mobility managementfunction in the 3GPP network can support both mobile broadband network(MBN) and fixed wireless broadband (FWB) network services. Thus, theseservices can be operated in one core network slice e.g., the MBN slice,but using two different service function chains. A first servicefunction chain can enable the full capability of the MMF due to themobility. A second service function chain can also include the MMF butin a transparent mode. In other words, FWB is a special case of the MBBwhere the vehicular speed is zero. Accordingly, the slice managementcomponent 402 can determine whether an existing network slice should bereused and whether a new service function chain (e.g., with the properoperational modes of each functional block) should be created within theexisting slice. Further, in one aspect, the slice management component402 can also determine associations with other network slices (e.g., RANslices, survivable ad hoc network (SAN) slices and/or subscriber policydomains, etc.). These associations can be one-to-one, one-to-many,many-to-one and/or many-to-many.

FIG. 5 illustrated an example system 500 that facilitates monitoring ofcore network slices, according to an aspect of the subject disclosure.It is noted that the core network control component 108, the corenetwork slices 210 ₁-210 _(M), and the slice management component 402,can comprise functionality as more fully described herein, for example,as described above with regard to systems 100-200 and 400.

According to an embodiment, when an instance of a core network slice(e.g., core network slices 210 ₁-210 _(M)) is created, a core networkdata store 502 is populated with information associated with the corenetwork slice. For example, the information can comprise, but is notlimited to, a service type associated with the core network slice,network functions provided by the core network slice, logic servicefunction chains provided by the core network slice, etc. In one aspect,the slice management component 402 can utilize this information toallocate service requests to an appropriate core network slice (and/orto determine that a new core network slice is to be instantiated tohandle a service request).

Further, once instantiated, a tracking component 504 can monitorfeedback metrics (e.g., throughput, latency, capacity utilization, etc.)associated with performance of a logic service function chain in thecore network slices 210 ₁-210 _(M) and/or with overall performance ofthe core network slices. In one aspect, the tracking component 504 cananalyze the feedback metrics to verify that service demands and/orexpected QoE are being met in real time. As an example, the feedbackmetrics can also be stored within the core network data store 502. Inone aspect, the slice management component 402 can utilize the feedbackmetrics to determine and/or learn performance patterns associated withthe core network slices 210 ₁-210 _(M) and their respective servicefunction chains (e.g., determine that a core network slice(s) thatperforms better with a first type of service than a second type ofservice). Moreover, the performance patterns can be utilized to allocatesubsequent service requests to an optimal core network slice (e.g.,determined to have a high performance for the particular service type).

Referring now to FIGS. 6A-6B, there illustrated are example systems600-650 that employ artificial intelligence (AI) components (602, 604)to facilitate automating one or more features in accordance with thesubject embodiments. It can be noted that the service abstractioncomponent 102, core network control component 108, data receptioncomponent 202, analysis component 304, trigger component 306, corenetwork slices 210 ₁-210 _(M), slice management component 402, corenetwork data store 502, and tracking component 504 can comprisefunctionality as more fully described herein, for example, as describedabove with regard to systems 100-500.

In an example embodiment, systems 600 and 650 (e.g., in connection withallocating and/or de-allocating resources for service requests) canemploy various AI-based schemes (e.g., intelligent processing/analysis,machine learning, etc.) for carrying out various aspects thereof. Forexample, a process for determining service attributes, UE preferences,which core network slices to select, instantiate, and/or update,determining user expectation and/or satisfaction, performance of thedifferent core network slices, etc. can be facilitated via an automaticclassifier system implemented by AI components 602 and/or 604. Moreover,the AI components 602 and/or 604 can various exploit artificialintelligence (AI) methods or machine learning methods. Artificialintelligence techniques can typically apply advanced mechanisms—e.g.,decision trees, neural networks, regression analysis, principalcomponent analysis (PCA) for feature and pattern extraction, clusteranalysis, genetic algorithm, or reinforced learning—to a data set. Inparticular, AI components 602 and/or 604 can employ one of numerousmethodologies for learning from data and then drawing inferences fromthe models so constructed. For example, Hidden Markov Models (HMMs) andrelated prototypical dependency models can be employed. Generalprobabilistic graphical models, such as Dempster-Shafer networks andBayesian networks like those created by structure search using aBayesian model score or approximation can also be utilized. In addition,linear classifiers, such as support vector machines (SVMs), non-linearclassifiers like methods referred to as “neural network” methodologies,fuzzy logic methodologies can also be employed.

As will be readily appreciated from the subject specification, anexample embodiment can employ classifiers that are explicitly trained(e.g., via a generic training data) as well as implicitly trained (e.g.,via observing device/operator preferences, historical information,receiving extrinsic information, type of service, type of device, etc.).For example, SVMs can be configured via a learning or training phasewithin a classifier constructor and feature selection module. Thus, theclassifier(s) of AI component 602 can be used to automatically learn andperform a number of functions, comprising but not limited to determiningaccording to a predetermined criteria, service type and attributes,event data, location related data, latency requirements of the service,etc. Further, classifier(s) of AI component 604 can be used toautomatically learn and perform a number of functions, comprising butnot limited to determining according to a predetermined criteria, anoptimal core network slice and/or the most efficient service functionchain that are suited handle traffic associated with a specific servicedata flow, whether an existing core network slice or any servicefunction chain in the core network slice is to be allocated to a servicerequest or a new core network slice with service function chains is toinstantiated, etc. The criteria can comprise, but is not limited to,historical patterns and/or trends, user and/or network operatorpreferences and/or policies, application/service provider preferences,predicted traffic flows, event data, latency data,reliability/availability data, current time/date, location data,performance and/or load data, function/component operational modeflexibility in a service function chain, and the like.

FIGS. 7-8 illustrate flow diagrams and/or methods in accordance with thedisclosed subject matter. For simplicity of explanation, the flowdiagrams and/or methods are depicted and described as a series of acts.It is to be understood and noted that the various embodiments are notlimited by the acts illustrated and/or by the order of acts, for exampleacts can occur in various orders and/or concurrently, and with otheracts not presented and described herein. Furthermore, not allillustrated acts may be required to implement the flow diagrams and/ormethods in accordance with the disclosed subject matter. In addition,those skilled in the art will understand and note that the methods couldalternatively be represented as a series of interrelated states via astate diagram or events. Additionally, it should be further noted thatthe methods disclosed hereinafter and throughout this specification arecapable of being stored on an article of manufacture to facilitatetransporting and transferring such methods to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device orcomputer-readable storage/communications media.

Referring now to FIG. 7 there illustrated is an example method 700 thatfacilitates allocation of core network resources, according to an aspectof the subject disclosure. As an example, method 700 can be implementedby one or more network devices (e.g., service abstraction component 102)of a communication network (e.g., cellular network). At 702, datarelated to one or more radio access networks can be accessed. In oneaspect, the radio access networks can utilize different radio accesstechnologies, such as, but not limited to, 4G, 5G, 3G, WiFi, low powerwide area networks, and/or other non-3GPP technologies. Further, thedata can comprise but is not limited to, spectrum data across licensedand unlicensed bands, access point information, cell site information,geographical location data, real-time load, cell identifier, type ofaccess point (e.g., macro, femto, pico, etc.), etc.

At 704, data related to one or more transport layers can be accessed.For example, the data can be associated with different devices (e.g.,routers and/or switches hosted on central office and/or switching officeenvironments) of backhaul networks that are on the egress and/or ingressof the infrastructure between the RAN and core network. At 706, based onan analysis of the accessed data, a trigger can be provided to a corenetwork controller to facilitate allocation of resources to a requestfor a service. As an example, the trigger can provide informationrelated to the type of service, service attributes, class of therequesting device, and/or current network conditions (e.g., load,performance, etc.), location of the access point and/or UE, event data,latency specifications of the service, etc. The core network controllercan utilize the trigger to select an optimal core network slice andconfigure a proper service function chain in the core network slice tohandle the service request. Further, at 708, the access point can beprovided with network address data of the selected core network entity(e.g., MME of the optimal core network slice), to which traffic for theservice is to be steered. As an example, the network address canrepresent an Internet protocol (IP) address of transmission controlprotocol (TCP)/IP suite of protocols (e.g., TCP/IP, user datagramprotocol (UDP)/IP, stream control transmission protocol (SCTP)/IP, anylayer 4 through layer 7 (L4˜7)/IP), or an asynchronous transfer mode(ATM) address of an ATM network, or an local area network (LAN) addressof LAN suite of protocols (e.g., Ethernet, fiber distributed datainterface (FDDI), IEEE 802.3 LANs, etc.), or a network address of thenetwork layer in the open systems interconnection (OSI) protocol stacks,or a multiprotocol label switching (MPLS) label in the MPLS network,etc.

FIG. 8 illustrates an example method 800 that selection of an optimalcore network slice for handling a service request, according to anaspect of the subject disclosure. As an example, method 800 can beimplemented by one or more network devices (e.g., core network controlcomponent 108) of a communication network (e.g., cellular network). At802, trigger data, associated with a service request received from a UEthat is located in a specified area, can be received. As an example, thetrigger data can comprise information related to the type of service,service attributes, class of the requesting device, current networkconditions (e.g., load, performance, etc.), location of the access pointand/or UE, event data, and/or latency specifications of the service,etc. At 804, it can be determined whether target service attributes(e.g., latency, performance, etc.) can be met by utilizing an existingcore network slice. As an example, parameters such as, current load,performance data, historical data, location, etc., of the existing corenetwork slices can be evaluated to facilitate the determination. Ifdetermined that the target service attributes can be met by utilizing anexisting core network slice, then at 806, the existing core networkslice can be allocated to serve traffic associated with the service. Asan example, addressing information associated with an entity of theexisting core network slice can be provided to an access point servingthe UE so that the access point can direct traffic related to theservice request to the entity.

Alternatively, if determined that the target service attributes cannotbe met by utilizing an existing core network slice and its associatedfunctions, then at 808, a new core network slice can be readilyinstantiated. In an aspect, the new core network slice can be customizedto handle the service for the class of the UE and/or can be localized(e.g., located in close proximity to the UE/access point). At 810, thenew core network slice can be allocated to serve traffic associated withthe service. As an example, addressing information associated with anentity of the new core network slice can be provided to the access pointso that the access point can direct traffic related to the servicerequest to the entity.

Advanced core network slicing architecture and design principlesdisclosed herein lay the foundation for building an intelligent as wellas robust next generation mobility network infrastructure that isoptimized for end-to-end services delivery. In one aspect, the systems100-650 and methods 700-800 disclosed herein provide variousnon-limiting advantages, for example, (i) provide an efficient corenetwork slicing design that is suited for 5G traffic demands and itsevolution; (ii) provide support for a variety of use cases, industryverticals, and/or usage driven business models; (iii) enable deploymentof multiple instances of logical core networks connected to a singleRAN; (iv) enable independent scaling of targeted core network slices, ondemand, across a given industry vertical and/or set of verticals withinthe same serving RAN; (v) provide support for scaling of core networkslices across multiple RAN technologies; (vi) facilitate intelligentsegregation of traffic types based on demand and/or information centricnetworking requirements; (vii) minimize disruption of core networkresources that are critical to revenue generating services; (viii) avoidcustomized overlays in the mobility core network; etc.

Referring now to FIG. 9, there is illustrated a block diagram of acomputer 902 operable to execute the disclosed communicationarchitecture. In order to provide additional context for various aspectsof the disclosed subject matter, FIG. 9 and the following discussion areintended to provide a brief, general description of a suitable computingenvironment 900 in which the various aspects of the specification can beimplemented. While the specification has been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that thespecification also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules comprise routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will note thatthe inventive methods can be practiced with other computer systemconfigurations, comprising single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the specification can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disk (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or other tangible and/ornon-transitory media which can be used to store desired information.Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, radio frequency (RF),infrared and other wireless media.

With reference again to FIG. 9, the example environment 900 forimplementing various aspects of the specification comprises a computer902, the computer 902 comprising a processing unit 904, a system memory906 and a system bus 908. As an example, the component(s),application(s) server(s), equipment, system(s), interface(s),gateway(s), controller(s), node(s), entity(ies), function(s), cloud(s)and/or device(s) (e.g., service abstraction component 102, radio networkcontrol component 104, transport network control component 106, corenetwork control component 108, UEs 202 ₁-202 _(N), radio network 204,RAN data store 206, transport router(s) 208, core network slices 210₁-210 _(M), IP network 212, application servers 214 ₁-214 _(K), datareception component 302, analysis component 304, trigger component 306,slice management component 402, core network data store 502, trackingcomponent 504, AI components 602-604, etc.) disclosed herein withrespect to systems 100-650 can each comprise at least a portion of thecomputer 902. The system bus 908 couples system components comprising,but not limited to, the system memory 906 to the processing unit 904.The processing unit 904 can be any of various commercially availableprocessors. Dual microprocessors and other multi-processor architecturescan also be employed as the processing unit 904.

The system bus 908 can be any of several types of bus structure that canfurther interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 906comprises read-only memory (ROM) 910 and random access memory (RAM) 912.A basic input/output system (BIOS) is stored in a non-volatile memory910 such as ROM, EPROM, EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer902, such as during startup. The RAM 912 can also comprise a high-speedRAM such as static RAM for caching data.

The computer 902 further comprises an internal hard disk drive (HDD)914, which internal hard disk drive 914 can also be configured forexternal use in a suitable chassis (not shown), a magnetic floppy diskdrive (FDD) 916, (e.g., to read from or write to a removable diskette918) and an optical disk drive 920, (e.g., reading a CD-ROM disk 922 or,to read from or write to other high capacity optical media such as theDVD). The hard disk drive 914, magnetic disk drive 916 and optical diskdrive 920 can be connected to the system bus 908 by a hard disk driveinterface 924, a magnetic disk drive interface 926 and an optical driveinterface 928, respectively. The interface 924 for external driveimplementations comprises at least one or both of Universal Serial Bus(USB) and IEEE 1394 interface technologies. Other external driveconnection technologies are within contemplation of the subjectdisclosure.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 902, the drives and storagemedia accommodate the storage of any data in a suitable digital format.Although the description of computer-readable storage media above refersto a HDD, a removable magnetic diskette, and a removable optical mediasuch as a CD or DVD, it should be noted by those skilled in the art thatother types of storage media which are readable by a computer, such aszip drives, magnetic cassettes, flash memory cards, solid-state disks(SSD), cartridges, and the like, can also be used in the exampleoperating environment, and further, that any such storage media cancontain computer-executable instructions for performing the methods ofthe specification.

A number of program modules can be stored in the drives and RAM 912,comprising an operating system 930, one or more application programs932, other program modules 934 and program data 936. All or portions ofthe operating system, applications, modules, and/or data can also becached in the RAM 912. It is noted that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 902 throughone or more wired/wireless input devices, e.g., a keyboard 938 and/or apointing device, such as a mouse 940 or a touchscreen or touchpad (notillustrated). These and other input devices are often connected to theprocessing unit 904 through an input device interface 942 that iscoupled to the system bus 908, but can be connected by other interfaces,such as a parallel port, an IEEE 1394 serial port, a game port, a USBport, an IR interface, etc. A monitor 944 or other type of displaydevice is also connected to the system bus 908 via an interface, such asa video adapter 946.

The computer 902 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 948. The remotecomputer(s) 948 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallycomprises many or all of the elements described relative to the computer902, although, for purposes of brevity, only a memory/storage device 950is illustrated. The logical connections depicted comprise wired/wirelessconnectivity to a local area network (LAN) 952 and/or larger networks,e.g., a wide area network (WAN) 954. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which canconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 902 is connectedto the local network 952 through a wired and/or wireless communicationnetwork interface or adapter 956. The adapter 956 can facilitate wiredor wireless communication to the LAN 952, which can also comprise awireless access point disposed thereon for communicating with thewireless adapter 956.

When used in a WAN networking environment, the computer 902 can comprisea modem 958, or is connected to a communications server on the WAN 954,or has other means for establishing communications over the WAN 954,such as by way of the Internet. The modem 958, which can be internal orexternal and a wired or wireless device, is connected to the system bus908 via the serial port interface 942. In a networked environment,program modules depicted relative to the computer 902, or portionsthereof, can be stored in the remote memory/storage device 950. It willbe noted that the network connections shown are example and other meansof establishing a communications link between the computers can be used.

The computer 902 is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., desktopand/or portable computer, server, communications satellite, etc. Thiscomprises at least Wi-Fi and Bluetooth™ wireless technologies or othercommunication technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity networks use radio technologies called IEEE802.11 (a, b, g, n, etc.) to provide secure, reliable, fast wirelessconnectivity. A Wi-Fi network can be used to connect computers to eachother, to the Internet, and to wired networks (which use IEEE 802.3 orEthernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radiobands, at an 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, forexample, or with products that contain both bands (dual band), so thenetworks can provide real-world performance similar to the basic 10BaseTwired Ethernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” “cache,” and substantially any other information storagecomponent relevant to operation and functionality of a component, referto “memory components,” or entities embodied in a “memory” or componentscomprising the memory. It will be noted that the memory components, orcomputer-readable storage media, described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. By way of illustration, and not limitation,nonvolatile memory can comprise read only memory (ROM), programmable ROM(PROM), electrically programmable ROM (EPROM), electrically erasable ROM(EEPROM), or flash memory. Volatile memory can comprise random accessmemory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such assynchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM),double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), SynchlinkDRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, thedisclosed memory components of systems or methods herein are intended tocomprise, without being limited to comprising, these and any othersuitable types of memory.

Referring now to FIG. 10, there is illustrated a schematic block diagramof a computing environment 1000 in accordance with the subjectspecification. The system 1000 comprises one or more client(s) 1002. Theclient(s) 1002 can be hardware and/or software (e.g., threads,processes, computing devices).

The system 1000 also comprises one or more server(s) 1004. The server(s)1004 can also be hardware and/or software (e.g., threads, processes,computing devices). The servers 1004 can house threads to performtransformations by employing the specification, for example. Onepossible communication between a client 1002 and a server 1004 can be inthe form of a data packet adapted to be transmitted between two or morecomputer processes. The data packet may comprise a cookie and/orassociated contextual information, for example. The system 1000comprises a communication framework 1006 (e.g., a global communicationnetwork such as the Internet, cellular network, etc.) that can beemployed to facilitate communications between the client(s) 1002 and theserver(s) 1004.

Communications can be facilitated via a wired (comprising optical fiber)and/or wireless technology. The client(s) 1002 are operatively connectedto one or more client data store(s) 1008 that can be employed to storeinformation local to the client(s) 1002 (e.g., cookie(s) and/orassociated contextual information). Similarly, the server(s) 1004 areoperatively connected to one or more server data store(s) 1010 that canbe employed to store information local to the servers 1004.

What has been described above comprises examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methods for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Accordingly, the presentspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “comprises” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receivingtrigger data from a service abstraction layer device, wherein thetrigger data is determined in response to receiving a request for aservice associated with a user equipment that is served by an accessnetwork device coupled to the service abstraction layer device; andbased on an analysis of the trigger data, instantiating a localizednetwork slice of network resources that is employable to perform networkfunctions to deliver the service via a portion of the network resourcesthat is determined to satisfy a proximity criterion associated with alocation related to the user equipment.
 2. The system of claim 1,wherein the network functions within the localized network slice arecustomized based on an attribute of the service.
 3. The system of claim1, wherein the instantiating comprises: in response to determining thatthe service is not classified as a delay tolerant service, instantiatingthe localized network slice or instantiating a service function chainwithin a pre-existing network slice.
 4. The system of claim 1, whereinthe instantiating comprises: in response to determining that the servicehas been assigned a priority that is determined to satisfy a highpriority criterion, instantiating the localized network slice orinstantiating a service function chain within a pre-existing networkslice.
 5. The system of claim 1, wherein the instantiating comprises: inresponse to determining that the service is determined to satisfy a highrevenue generation criterion, instantiating the localized network sliceor instantiating a service function chain within a pre-existing networkslice.
 6. The system of claim 1, wherein the instantiating comprises: inresponse to determining that a performance metric associated with thelocalized network slice satisfies a defined performance criterion,instantiating the localized network slice or instantiating a servicefunction chain within a pre-existing network slice.
 7. The system ofclaim 1, wherein the trigger data comprises classification data thatrepresents a category of the user equipment.
 8. The system of claim 1,wherein the trigger data comprises network data that represents loaddata associated with a network device.
 9. The system of claim 1, whereinthe trigger data comprises service characteristic data that represents acharacteristic of the service.
 10. The system of claim 1, wherein thetrigger data comprises location data that represents the location of theuser equipment.
 11. The system of claim 1, wherein the trigger datacomprises access type data that represents a type of radio accesstechnology supported by the user equipment.
 12. The system of claim 1,wherein the operations further comprise: directing, to the accessnetwork device, address data indicative of a control plane device of thelocalized network slice to facilitate steering of communication dataassociated with the service between the access network device and thecontrol plane device.
 13. A method, comprising: receiving, by a systemcomprising a processor, trigger data from a service abstraction layerdevice of a network, wherein the trigger data has been determined inresponse to receiving a request for a service associated with a userequipment served by an access network device coupled to the serviceabstraction layer device; and in response to determining that thetrigger data satisfies a defined selection criterion, instantiating, bythe system, network resources for a network slice of the network thatare employable to perform the service, wherein the network resources aredetermined to satisfy a proximity criterion associated with a locationrelated to the user equipment.
 14. The method of claim 13, wherein thenetwork resources comprise first network resources, the network slicecomprises a first network slice, and further comprising: in response todetermining that the trigger data fails to satisfy the defined selectioncriterion, allocating, by the system, pre-instantiated second networkresources for a second network slice of the network that are employableto perform the service.
 15. The method of claim 13, wherein thereceiving the trigger data comprises receiving location data indicativeof the location of the user equipment.
 16. The method of claim 13,wherein the receiving the trigger data comprises receiving latency dataindicative of a latency attribute associated with the service.
 17. Themethod of claim 13, wherein the receiving the trigger data comprisesreceiving category data indicative of a class of the user equipment. 18.The method of claim 13, wherein receiving the trigger data comprisesreceiving quality of experience data indicative of a quality ofexperience associated with the service.
 19. A machine-readable storagemedium, comprising executable instructions that, when executed by aprocessor, facilitate performance of operations, comprising: receiving,from a service abstraction layer device of a network, trigger data thathas been determined subsequent to receiving a request for a serviceassociated with a user equipment served by an access network device thatis coupled to the service abstraction layer device; and based on ananalysis of the trigger data, determining association data thatrepresents an association between network slices of the network.
 20. Themachine-readable storage medium of claim 19, wherein the associationcomprises a one-to-one association between the network slices.